Driver activity and vehicle operation logging and reporting

ABSTRACT

An onboard electronic system for logging and reporting driver activity and operation data of a vehicle. The system incorporates an onboard recorder operatively connected to a data bus of the vehicle and configured to continuously electronically monitor and obtain vehicle operation data including vehicle fuel consumption data and vehicle mileage data. A transmitter is adapted for transmitting the vehicle operation data from the onboard recorder to a remote terminal outside of the vehicle. Data processing software is operable for generating a fuel data report using the vehicle operation data, and determining based on the fuel data report whether a driver satisfies a vehicle operation requirement established by an authority.

TECHNICAL FIELD AND BACKGROUND OF THE DISCLOSURE

The present disclosure relates broadly and generally systems, methods,and apparatus for logging and reporting driver activity and vehicleoperation. In other exemplary embodiments, the disclosure comprisessystems, methods, and apparatus for automated at-the-pump management ofvehicle fuel purchases. In still further embodiments, the disclosurecomprises systems, methods, and apparatus for diagnosing and managingvehicle faults.

SUMMARY OF EXEMPLARY EMBODIMENTS

Various exemplary embodiments of the present disclosure are describedbelow. Use of the term “exemplary” means illustrative or by way ofexample only, and any reference herein to “the invention” is notintended to restrict or limit the invention to exact features or stepsof any one or more of the exemplary embodiments disclosed in the presentspecification. References to “exemplary embodiment,” “one embodiment,”“an embodiment,” “various embodiments,” and the like, may indicate thatthe embodiment(s) of the invention so described may include a particularfeature, structure, or characteristic, but not every embodimentnecessarily includes the particular feature, structure, orcharacteristic. Further, repeated use of the phrase “in one embodiment,”or “in an exemplary embodiment,” do not necessarily refer to the sameembodiment, although they may.

It is also noted that terms like “preferably”, “commonly”, and“typically” are not utilized herein to limit the scope of the claimedinvention or to imply that certain features are critical, essential, oreven important to the structure or function of the claimed invention.Rather, these terms are merely intended to highlight alternative oradditional features that may or may not be utilized in a particularembodiment of the present invention.

According to one exemplary embodiment, the present disclosure comprisesan automated at-the-pump method for managing vehicle fuel purchases at afuel station. The method comprises transmitting driver identificationdata to a mobile device assigned to a vehicle driver. The mobile devicecomprises wireless communication hardware (e.g., WIFI, BLUETOOTH,infrared), an input means, a processor, and memory. The exemplary methodelectronically verifies that the driver identification data received bythe mobile device matches the assigned vehicle driver. In other words,the method uses the driver identification data received by the mobiledevice to confirm that the vehicle driver is an authorized (and proper)user of the mobile device. Event setting data is recorded in the memoryof the mobile device. Vehicle data is transmitted from a data bus of thevehicle to the mobile device for storage in the memory. The vehicle dataand driver identification data are transmitted to a remote terminal.Using the remote terminal, the vehicle data and driver identificationdata are electronically authenticated. An authorization signal istransmitted from the remote terminal to an at-the-pump fuel controlterminal. The authorization signal enables dispensing of fuel from astation pump to the vehicle. After the vehicle is fueled, fuel purchasedata is transmitted from the at-the-pump fuel control terminal to atleast one of the remote terminal and mobile device.

According to another exemplary embodiment, the method further compriseselectronically storing the driver identification data on an RFID card.

According to another exemplary embodiment, the driver identificationdata comprises at least one in a group consisting of a passcode, firstand last name, e-mail address, and telephone number.

According to another exemplary embodiment, the input means of the mobiledevice comprises a keypad. The step of electronically verifying furthercomprises matching a passcode entered by the driver using the keypad ofthe mobile device to a passcode stored in memory of the mobile device.

According to another exemplary embodiment, the input means of the mobiledevice comprises a microphone. The step of electronically verifyingfurther comprises matching a voice code spoken by the driver into themicrophone of the mobile device to a voice code stored in memory of themobile device.

According to another exemplary embodiment, the step of electronicallyverifying comprises reading biometric data of the vehicle driver andmatching the biometric data to data stored in memory of the mobiledevice.

According to another exemplary embodiment, the biometric data isselected from a group consisting of facial, retinal, and thumb printidentifiers.

According to another exemplary embodiment, the event setting datacomprises at least one in a group consisting of current time, date, and(GPS) location. The event setting data may be recorded in the memory ofthe mobile device automatically at any step of the exemplary method; forexample, at the time the authorization signal is transmitted from theremote terminal to an at-the-pump fuel control terminal, or at the timethe fuel purchase data is transmitted from the at-the-pump fuel controlterminal.

According to another exemplary embodiment, the vehicle data comprises atleast one in a group consisting of, for example, vehicle serial number,engine VIN, mileage, diagnostic codes, fuel level, battery voltage, tirepressure, and ABS and alternator status.

According to another exemplary embodiment, the vehicle data buscomprises at least one in a group consisting of RS232, SAE J1708, SAEJ1850, SAE J1939, SAE J2497, OB-2, and CAN.

According to another exemplary embodiment, the fuel purchase datacomprises at least one in a group consisting of gallons of fuelpurchased, cost per gallon, and total fuel cost.

According to another exemplary embodiment, the method further comprisesstoring the fuel purchase data on an electronic on-board recorder in thevehicle.

According to another exemplary embodiment, the method further comprisesstoring the vehicle data on an electronic on-board recorder in thevehicle.

According to another exemplary embodiment, the method further comprisesstoring the driver identification data on an electronic on-boardrecorder in the vehicle.

According to another exemplary embodiment, after the vehicle is fueled,the method comprises transmitting the fuel purchase data from theat-the-pump fuel control terminal to the electronic on-board recorder inthe vehicle.

According to another exemplary embodiment, the step of transmittingvehicle data from the data bus of the vehicle to the mobile devicecomprises utilizing wireless near-field communication technology.

According to another exemplary embodiment, the method further comprisestransmitting vehicle data from the mobile device to the at-the-pump fuelcontrol terminal.

According to another exemplary embodiment, the step of transmittingvehicle data from the mobile device to the at-the-pump fuel controlterminal comprises utilizing wireless near-field communicationtechnology.

According to another exemplary embodiment, the method further comprisestransmitting the fuel purchase data from the at-the-pump fuel controlterminal to the mobile device utilizing wireless near-fieldcommunication technology.

According to another exemplary embodiment, data is communicated betweenthe mobile device, at-the-pump fuel control terminal, and remoteterminal utilizing a wireless connection selected from a groupconsisting of a WIFI connection, a BLUETOOTH connection, cellularconnection, and an infrared connection.

The term “remote terminal” refers broadly herein to any mobile device,as described below, network server, cloud server, desktop, laptopcomputer, netbook, e-reader, tablet computer, mobile phone, personaldigital assistant, or other fixed or mobile electronic data processing,collection, transmission and/or storage device (programmable ornon-programmable) which is physically separate from and unattached tocomponents of the station pump including the at-the-pump fuel controlterminal. In one example, the remote terminal is physically distant fromthe fuel station. In another example, the remote terminal is located ata corporate office, fleet management center, or other suchestablishment—also physically distant from the fuel station.

Exemplary Mobile Device

The mobile computing device (or “Mobile Device”) may incorporate orcomprise any general or specific purpose machine with processing logiccapable of manipulating data according to a set of program instructions.Examples of Mobile Devices include a laptop computer, netbook, e-reader,tablet computer, mobile phone, personal digital assistant, desktop, andothers. In one exemplary embodiment, the Mobile Device comprises asmartphone or other high-end mobile phone using an operating system suchas Google's Android, Apple's iOS4 and iOS5, Maemo, Bada, Symbian,Windows Phone, Palm, Blackberry, and others. The exemplary Mobile Devicemay include a high-resolution touchscreen (display screen), a webbrowser, high-speed data access via Wi-Fi and mobile broadband, andadvanced application programming interfaces (APIs) for runningthird-party applications. The Mobile Device may also be equipped withNFC, and paired with NFC tags or stickers which can be programmed by NFCapps and other mobile apps on the device. For example, BlackBerrydevices support NFC using BlackBerry Tag on a number of devices runningBlackBerry OS 7.0 and greater. Microsoft has also added native NFCfunctionality in its mobile OS with Windows Phone 8, as well as theWindows 8 operating system. Other handheld mobile devices withoutbuilt-in NFC chips may utilize MicroSD and UICC SIM cards incorporatingindustry standard contactless smartcard chips with ISO14443 interface,with or without built-in antenna.

The exemplary mobile device may also include card slots for removable ornon-removable flash and SIM cards, and may have up to 32 GB ofnon-volatile internal memory. One or more of the flash and SIM cards andinternal memory may comprise computer-readable storage media containingprogram instructions applicable for effecting the present system andmethod for vehicle tire and parts management. As generally known andunderstood in the art, the flash card is an electronic flash memory datastorage device used for storing digital information. The card is small,re-recordable, and able to retain data without power. For example,Secure Digital (SD) is a non-volatile memory card format developed bythe SD Card Association for use in portable devices. SD has an officialmaximum capacity of 2 GB, though some are available up to 4 GB.

The SIM card contains an integrated circuit that securely stores theservice-subscriber key (IMSI) used to identify a subscriber on theMobile Device. SIM hardware typically consists of a microprocessor, ROM,persistent (non-volatile) EEPROM or flash memory, volatile RAM, and aserial I/O interface. SIM software typically consists of an operatingsystem, file system, and application programs. The SIM may incorporatethe use of a SIM Toolkit (STK), which is an application programminginterface (API) for securely loading applications (e.g., applets) ordata to the SIM for storage in the SIM and execution by the MobileDevice. The STK allows a mobile operator (such as a wireless carrier) tocreate/provision services by loading them into the SIM without changingother elements of the Mobile Device. One convenient way for loadingapplications to the SIM is over-the-air (OTA) via the Short MessageService (SMS) protocol.

Secure data or application storage in a memory card or other device maybe provided by a Secure Element (SE). The SE can be embedded in thelogic circuitry of the Mobile Device (e.g., smartphone), can beinstalled in a SIM, or can be incorporated in a removable SD card(secure digital memory card), among other possible implementations.Depending on the type of Secure Element (SE) that hosts an applet, thefeatures implemented by the applet may differ. Although an SE istypically Java Card compliant regardless of its form factor and usage,it may implement features or functions (included in the operating systemand/or in libraries) that are specific to that type of SE. For example,a UICC (Universal Integrated Circuit Card) may implement features thatare used for network communications, such as text messaging and STK,whereas in certain embedded SE devices, these features may not beimplemented.

Additionally, to identify a user's Mobile Device, a unique serial numbercalled International Mobile Equipment Identity, IMEI, may be assigned tothe device. As known by persons skilled in the art, IMEI is standardizedby ETSI and 3GPP, and mobile devices which do not follow these standardsmay not have an IMEI. The IMEI number is used by the network to identifyvalid mobile devices. IMEI identifies the device, not the user (the useris identified by an International Mobile Subscriber Identity, IMSI), bya 15-digit number and includes information about the source of themobile device, the model, and serial number. Other features of theexemplary Mobile Device may include front-facing and rear-facingcameras, Dolby Digital 5.1 surround sound, video mirroring and video outsupport, built-in speaker and microphone, built-in 25-watt-hourrechargeable lithium-polymer battery, and sensors including three-axisgyro, accelerometer, and ambient light sensor.

The exemplary Mobile Device may also combine aGPS and other locationservices including WIFI Positioning System and cell-site triangulation,or hybrid positioning system. Mobile Phone Tracking tracks the currentposition of a mobile device, even when it is moving. To locate thedevice, it must emit at least the roaming signal to contact the nextnearby antenna tower, but the process does not require an active call.GSM localization is then done by multilateration based on the signalstrength to nearby antenna masts. Mobile positioning, which includeslocation based service that discloses the actual coordinates of a mobiledevice bearer, is a technology used by telecommunication companies toapproximate where a mobile device, and thereby also its user (bearer),temporarily resides.

The exemplary Mobile Device may comprise BLUETOOTH, WIFI, and NFCtechnologies. BLUETOOTH and WIFI are similar to NFC in that all threetechnologies allow wireless communication and data exchange betweendigital devices like the present Mobile Device. NFC, however, utilizeselectromagnetic radio fields while technologies such as BLUETOOTH andWIFI focus on radio transmissions. The present Mobile Device maycomprise an active NFC device, enabling it to collect information fromNFC tags and to exchange information with other compatible devices. TheMobile Device may also write information to NFC tags. To ensuresecurity, NFC often establishes a secure channel and uses encryptionwhen sending sensitive information.

In another aspect, the present disclosure comprises a method for loggingand reporting driver activity and vehicle operation. The method includesidentifying a driver of a vehicle and recording operating data. Theoperating data is recorded with an electronic on-board recorder that ishard-wired to a data bus, for example, an engine control module, of thevehicle, coupled to a vehicle mileage sensing system, and linked to aglobal navigation satellite system. The operating data includes mileageobtained from at least one of the vehicle mileage sensing system and thevehicle data bus; engine use, time, and date obtained from the vehicledata bus; and location, time, and date obtained from the globalnavigation satellite system. The method includes recording a duty statusof the driver. The duty status includes (a) off duty status, (b) sleeperberth status, (c) driving-on duty status, and (d) not driving-on dutystatus.

The method further includes creating an hours of service log from time,date, and duty status, the hours of service log including a change induty status of the driver, time and date the change occurred, hourswithin each duty status, total hours driven today, total hours on dutyfor seven days, and total hours on duty for eight days; creating a fueltax log from mileage obtained from the vehicle mileage sensing system,location obtained from the global navigation satellite system, timeobtained from at least one of the vehicle data bus and the globalnavigation satellite system, and date obtained from at least one of thevehicle data bus and the global navigation satellite system, the fueltax log including miles traveled between periodic recording intervals,and location, time, and date recorded at each periodic recordinginterval; comparing the driver's hours of service log to an applicablerequirement, for example, law or regulation; indicating to the driverwith the on-board recorder whether the driver is in-compliance orout-of-compliance with the applicable requirement; automaticallyuploading the hours of service log and the fuel tax log to a receiverexternal to the vehicle using a wireless telecommunications network; andemitting a compliance signal representative of whether the driver isin-compliance or out-of-compliance with the applicable requirement to asecond receiver external to the vehicle and under control ofauthorities.

Embodiments of this aspect may include one or more of the followingfeatures.

The method includes identifying the driver of the vehicle by interfacingwith a portable memory device, and importing a driver's hours of servicelog through the portable memory device or the wireless network. Theportable memory device is, for example, a smart card or contact memorybutton. The method further includes verifying the identity of the driverof the vehicle using, for example, biometric verification, and enablingthe vehicle to be started, moved, or engine idled in response toidentifying the driver of the vehicle.

Recording operating data includes automatically recording the mileagefrom the vehicle mileage sensing system; the mileage, engine use, time,and date obtained from the vehicle data bus; and the location, time, anddate obtained from the global navigation satellite system. Recording theduty status can include automatically determining a change in the dutystatus and at least one of the time, date and location of the change inthe duty status from the operating data. Recording the duty statusincludes logging a change in the duty, status from a manual input by thedriver.

The fuel tax log is used to create an IFTA (International Fuel TaxAgreement) compliant fuel tax report. The method includes manuallyinputting an indication of a border crossing.

When team driving, the method includes logging the duty status of afirst driver of the vehicle with the on-board recorder; identifying anext driver of the vehicle with the on-board recorder; logging the dutystatus of the first driver and the next driver of the vehicle with theon-board recorder; and importing data for an hours of service log forthe next driver into the on-board recorder from at least one of aportable memory device and a wireless telecommunications network. Thefuel tax log can be created for a single vehicle having the first driverand the second driver.

The method includes calibrating mileage received from the vehiclemileage sensing system using data received from the global navigationsatellite system or using vehicle tire size, and providing mileage fromthe recorder to an odometer display and to the vehicle data bus.

An exceptions report can be created from the comparison of the driver'shours of service log to the applicable requirement, and a cause of beingout-of-compliance displayed to the driver.

The method includes encrypting the operating data, the hours of servicelog, the fuel tax log, and the compliance signal emitted from therecorder to ensure data integrity.

Operating data can be modified by a driver input and/or by a fleetcarrier input, and any alterations of operating data recorded with atrack changes function of the on-board recorder and/or on the hostserver.

The hours of service log can be displayed, for example, inside oroutside the vehicle on an external display, as a graphical grid.

Automatically uploading includes uploading over a pager connection, acellular telephone connection, a wide area network connection, aninfrared connection, a radio connection, and/or a satellite connection.Automatically uploading includes uploading during an off-peak operatingperiod, for example between 1:00 am and 5:00 am and/or on a weekend, fora wireless telecommunications network. Automatically uploading includesattempting to upload at least daily first over a least expensiveconnection and, if unsuccessful, then over at least one next leastexpensive connection, and uploading over a satellite connection whensuccessive daily uploads are unsuccessful. Automatically uploadingincludes attempting to upload at least daily first over a predeterminedwireless telecommunications network connection and, if unsuccessful,then over another predetermined wireless telecommunications network.Automatic uploading is an uploading of the current day, previous days,or day prior to the previous day hours of service and/or fuel tax logs.

The method includes uploading to the second receiver external to thevehicle when a compliance status check is requested by law enforcement,and/or when the vehicle is within a predetermined range of the secondreceiver. The second receiver is located, for example, on a handhelddevice, along a highway, at a weigh station, or within a law enforcementvehicle. The compliance signal is uploaded, for example, through a wiredor wireless connection connected to a data port inside or outside of thevehicle.

The hours of service log is output to, for example, a display on theon-board recorder, a display on an external display device, the secondreceiver, or a wired connection connected to a data port inside oroutside of the vehicle. The output of the hours of service log occursresponsive to a request from, for example, the driver, a fleet carrier,or the authorities. A data transfer and storage device can be placed incommunication with the on-board recorder; and the hours of service log,fuel tax log, and the compliance signal uploaded to the data transferand storage device.

The receiver to which the logs are automatically uploaded is, forexample, a host server, and the fuel tax logs are uploaded from the hostserver to an external server that creates and files fuel tax reports.

In particular embodiments, the method may include notifying the driverif a particular event occurs, for example, notifying the driver to loginto the recorder if the vehicle moves and the driver has not logged in,emitting an out-of-compliance signal if the driver is not logged inwithin a predetermined period, notifying the driver to log operatingdata on a paper log if the recorder is malfunctioning, and notifying adriver when the driver is nearing the end of an hours of serviceparameter. The driver can be notified by, for example, a text message, avisual indicator, and/or an audible signal. Compliance can be indicatedby red, yellow, and green lights. A light on the recorder can be flashedwhen the driver is within a first predetermined time period of the endof the parameter, and another light on the recorder flashed when thedriver is within another predetermined time period of the end of theparameter. The carrier can also be notified when the driver is nearingthe end of a parameter. The method can also include emitting a signalindicating whether the recorder is present.

The method further includes, for example, the driver certifying thehours of service log prior to the automatic upload, and initiating aself-diagnostic function on the recorder upon a predetermined event. Thepredetermined event is at least one of a vehicle start, once in a24-hour cycle, upon demand by law enforcement, and upon demand by thedriver.

According to another aspect, a method for logging and reporting driveractivity and vehicle operation includes recording only the followingoperating data mileage obtained from at least one of the vehicle mileagesensing system and the vehicle data bus; engine use, time, and dateobtained from the vehicle data bus; and location, time, and dateobtained from the global navigation satellite system.

According to another aspect, an on-board recorder for logging andreporting driver activity and vehicle operation includes a memory deviceconfigured to store operating data; a power supply; a first interfaceconfigured to connect to a vehicle mileage sensing system; a secondinterface configured to connect to an vehicle data bus of the vehicle; areceiver configured to link with a global navigation satellite system;at least one data portal configured to upload data from the memorydevice to a receiver external to the vehicle using a wirelesstelecommunications network, and supporting a connection with a receiverexternal to the vehicle and under control of authorities; a driverinterface configured to record driver identification information inputby a driver of the vehicle and duty status input by the driver; aprocessor operatively connected to the memory device for processingencoded instructions, recording operating data, and creating an hours ofservice log, a fuel tax log, and determining whether the driver is incompliance with an applicable requirement; and a display.

According to another aspect, a system for logging and reporting driveractivity and vehicle operation includes an on-board recorder; wiredconnection between the on-board recorder and the vehicle data bus; afirst server connected with the vehicle through the wirelesstelecommunications network, the on-board recorder being configured toautomatically download the hours of service log, the fuel tax log, andthe compliance signal; and a second server connected with the firstserver and configured to receive the fuel tax log, the second serverincluding a computer readable media encoded with one or more computerprograms for filing fuel tax reports based on the fuel tax log.

According to another aspect, a device for logging and reporting driveractivity and vehicle operation includes one or more of the followingmeans: means for identifying a driver of a vehicle and recordingoperating data; means for recording a duty status of the driver; meansfor creating an hours of service log; means for creating a fuel tax log;means for comparing the driver's hours of service log to an applicablerequirement; means for indicating to the driver with the on-boardrecorder whether the driver is in-compliance or out-of-compliance withthe applicable requirement; means for automatically uploading the hoursof service log and the fuel tax log to a receiver external to thevehicle; and means for emitting a compliance signal representative ofwhether the driver is in-compliance or out-of-compliance with theapplicable governmental reporting requirement to a second receiverexternal to the vehicle and under control of authorities.

According to another aspect, a method includes one or more of thefollowing and/or an apparatus includes one or more of the followingmeans for: identifying one or more drivers of a vehicle; verifying theidentity of the one or more drivers by at least one of biometric andvisual means; determining driver hours of service for more than onedriver concurrently; recording driver hours of service for more than onedriver concurrently; uploading data via a least cost method over awireless telecommunications network; uploading through the recorder, viaa wireless telecommunications network, driver identity, whether or notverified; identifying a driver, tying identity information to a driverrecord, determining driver hours of service, recording hours of service,uploading hours of service via a wireless telecommunications network,and optionally verifying identity information and optionally tyingverification information to the driver record.

According to another aspect, a method includes one or more of thefollowing and/or an apparatus includes one or more of the followingmeans for: determining miles driven by a vehicle; recording miles drivenby a vehicle; determining at least one of present and past location of avehicle within a jurisdiction; determining at least one of present andpast location of a vehicle between jurisdictions; determining bordercrossings between jurisdictions; recording at least one of present andpast location of a vehicle within a jurisdiction; recording at least oneof present and past location of a vehicle within two or morejurisdictions; recording border crossings between jurisdictions;uploading via a wireless telecommunications network at least one ofpresent and past location of a vehicle within a jurisdiction; uploadingvia a wireless telecommunications network at least one of present andpast location of a vehicle within two or more jurisdictions; uploadingvia a wireless telecommunications network border crossings betweenjurisdictions; and uploading via a least cost method over a wirelesstelecommunications network at least one of present and past location ofa vehicle within a jurisdiction, at least one of present and pastlocation of a vehicle within two or more jurisdictions, and/or bordercrossings between jurisdictions.

According to another aspect, a method includes one or more of thefollowing and/or an apparatus includes one or more of the followingmeans for: calculating, for example, periodically, when interrogated byauthorities, or continuously, whether or not a driver is driving withinparameters established by at least one of law(s) or regulation(s);wirelessly notifying, signaling, alerting or informing authorities thata driver is not in compliance with applicable hours of service laws orregulations; transmitting driver hours of service data to lawenforcement via at least one of a wired connection, portable memorydevice and wirelessly, displaying data residing on the recorder via atleast one of a wired connection, portable memory device and wirelessly,displaying remaining time for driver hours of service in at least oneduty status generated from the recorder; exchanging data between therecorder and devices used to pump fuel into a vehicle; determining adriver's hours of service in compliance with home country and country ofoperation laws and regulations determining more than one driver's hoursof service concurrently in compliance with home country and country ofoperation laws and regulations; and displaying hours of service data inany one or more languages.

According to another aspect, a method includes one or more of thefollowing and/or an apparatus includes one or more of the followingmeans for: identifying the location at which a trailer is at least oneof tethered or un-tethered from a vehicle; recording the location atwhich a trailer is at least one of tethered or un-tethered from avehicle; uploading the location at which a trailer is at least one oftethered or un-tethered from a vehicle; identifying the location of atrailer tethered to a vehicle; recording the location of a trailertethered to a vehicle; and uploading the location of a trailer tetheredto a vehicle.

The details of one or more embodiments of the invention are set forth inthe accompanying drawings and the description below. Other features,objects, and advantages of the invention will be apparent from thedescription and drawings, and from the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments of the present disclosure will hereinafter bedescribed in conjunction with the following drawing figures, whereinlike numerals denote like elements, and wherein:

FIG. 1 is a front view of a display of an on-board recorder;

FIG. 2 is a schematic view of the on-board recorder;

FIG. 3 is a flowchart of a system and method for logging and reportingdriver and vehicle operating data;

FIG. 4 is a flowchart of processing steps for logging and reportingdriver and vehicle operating data;

FIG. 5 is a flowchart of processing steps for logging and reportingdriver and vehicle operating data;

FIG. 6 is a graphical view of an hours-of-service log generated by theon-board recorder;

FIG. 7 is a front view of a display external to the recorder;

FIG. 8 is a schematic view of a device for receiving a signal indicatingcompliance status of a driver or vehicle;

FIGS. 9 and 10 are schematic drawings illustrating various features anddevices of an exemplary system and method for managing vehicle fuelpurchases; and

FIG. 11 is a flow diagram illustrating an exemplary implementation ofthe present system and method for managing vehicle fuel purchases.

DESCRIPTION OF EXEMPLARY EMBODIMENTS AND BEST MODE

The present invention is described more fully hereinafter with referenceto the accompanying drawings, in which one or more exemplary embodimentsof the invention are shown. Like numbers used herein refer to likeelements throughout. This invention may, however, be embodied in manydifferent forms and should not be construed as limited to theembodiments set forth herein; rather, these embodiments are provided sothat this disclosure will be operative, enabling, and complete.Accordingly, the particular arrangements disclosed are meant to beillustrative only and not limiting as to the scope of the invention,which is to be given the full breadth of the appended claims and any andall equivalents thereof. Moreover, many embodiments, such asadaptations, variations, modifications, and equivalent arrangements,will be implicitly disclosed by the embodiments described herein andfall within the scope of the present invention.

Although specific terms are employed herein, they are used in a genericand descriptive sense only and not for purposes of limitation. Unlessotherwise expressly defined herein, such terms are intended to be giventheir broad ordinary and customary meaning not inconsistent with thatapplicable in the relevant industry and without restriction to anyspecific embodiment hereinafter described. As used herein, the article“a” is intended to include one or more items. Where only one item isintended, the term “one”, “single”, or similar language is used. Whenused herein to join a list of items, the term “or” denotes at least oneof the items, but does not exclude a plurality of items of the list.

For exemplary methods or processes of the invention, the sequence and/orarrangement of steps described herein are illustrative and notrestrictive. Accordingly, it should be understood that, although stepsof various processes or methods may be shown and described as being in asequence or temporal arrangement, the steps of any such processes ormethods are not limited to being carried out in any particular sequenceor arrangement, absent an indication otherwise. Indeed, the steps insuch processes or methods generally may be carried out in variousdifferent sequences and arrangements while still falling within thescope of the present invention.

Additionally, any references to advantages, benefits, unexpectedresults, or operability of the present invention are not intended as anaffirmation that the invention has been previously reduced to practiceor that any testing has been performed. Likewise, unless statedotherwise, use of verbs in the past tense (present perfect or preterit)is not intended to indicate or imply that the invention has beenpreviously reduced to practice or that any testing has been performed.

Referring now specifically to the drawings, the present disclosurecomprises exemplary systems, methods and apparatus capable of loggingdriver activity and vehicle operating data, creating reports from thedata containing information required to comply with HOS regulations andIFTA fuel tax reporting, and emitting a signal indicating whether thedriver is in-compliance or out-of-compliance with applicable HOS laws orregulations. In other exemplary embodiments, the disclosure comprisessystems, methods, and apparatus for automated at-the-pump management ofvehicle fuel purchases. In still further embodiments, the disclosurecomprises systems, methods, and apparatus for diagnosing and managingvehicle faults.

I. System and Method for Logging Driver Activity and Vehicle Operation

Referring to FIGS. 1 and 2, an on-board recorder 200 includes variousinputs and outputs for interfacing with a driver of the vehicle, a hostserver (typically located at the fleet carrier), authorities, a vehiclemileage sensing system, for example, a speed sensor (such as a magneticpickup) and vehicle odometer sensor display of the vehicle, a data busof the vehicle, for example, the vehicle engine control module (ECM),and a global navigation satellite system. The driver communicates withrecorder 200 via a driver interface 240 permitting data input andinteraction with the driver through the use of a portable memory devicereader 241, and duty status buttons 244.

Recorder 200 includes a front panel 240 having a display screen 250, forexample, a scrolling text message bar, for displaying text messages tothe driver, a portable memory device reader 241, such as a contactmemory button reader or smart card reader, to permit logging-in andlogging-out of the driver from recorder 200 as well as transfer of priordriver activity to and from recorder 200, and duty status buttons 244permitting the driver to manually change the driver's duty status, i.e.,“on-duty driving,” “off-duty,” “on-duty, not driving,” or “sleeperberth.”

Front panel 240 has a self-test button 245 that allows the driver toinitiate testing of the operability of recorder 200, and an indicatorlight 246, 248, such as an LED light, that indicates proper or improperoperation of recorder 200 and/or the driver that is currently drivingwhen team driving. Additional indicating lights 246 provide a visualindication of whether the driver's hours of service is in compliance orout-of-compliance with applicable hours of service regulations, forexample, a red light indicates out-of-compliance, a green lightindicates in-compliance, and a yellow light indicates that the driver isapproaching the end of permitted driving time. Additionally oralternatively, compliance information can be conveyed to the driveraudibly and/or on display screen 250. Front panel 240 also includeseither or both of on-duty time remaining and a scrolling text messagebar on display 250. Driver buttons 247 permit recorder 200 to switch thedisplay between the drivers driving.

The front panel 240 of the driver interface includes optional biometricreading device(s) 242, 249, for example, a fingerprint recognitionreader 242 and a camera 249. Recorder 200 also includes a wired dataport 243, such as a USB port, to permit data transfer between therecorder 200 and other external devices or media, such as an electronicdisplay (shown in FIG. 7).

Recorder 200 continuously obtains mileage from the vehicle mileagesensing system through a mileage sensing system interface 220, as wellas mileage, engine use, miles driven, time and date obtained from theECM through an ECM interface 225. Vehicle location (latitude andlongitude), date, and time are input to recorder 200 from a globalnavigation satellite system, e.g., GPS, via a satellite interface 230periodically, such as every fifteen minutes. In addition, a wirelessdata portal 235 is provided to permit the uploading and downloading ofdata from and to recorder 200.

On-board recorder 200 includes a back-up power supply 215, for example,an internal battery, processor 205, and a memory device 210. Primarypower to on-board recorder 200 is provided by a connection to thevehicle battery. The processor 205 is, for example, a central processingunit (CPU) or a simpler data storage device utilizing encoded andencrypted instructions with processing capabilities in accordance withthe available memory 210. The memory device 210 includes read and writecapabilities and a variety of commercial, off the shelf memory media.The processor 205 and memory 210 collectively form the logic componentof the recorder 200. Recorder 200 includes a display 250 for informingthe driver of the remaining driving time permitted by the HOS laws orregulations, and for displaying relevant information to federal,national, state, provincial or local authorities, as discussed below.

Referring to FIG. 3, a process 100 for logging and reporting driveractivity and vehicle operating data includes driver identification 110,data acquisition and recording 130, data processing 140, and datareporting 150. On-board recorder 200 is always powered on. Recorder 200can automatically enter a “sleep mode” in which non-essential systemssuch as the display screen are powered down to conserve power, and thedriver can awaken recorder 200 by pushing any key, or recorder 200 canbe awakened by starting the vehicle or if the vehicle moves. The abilityof the driver to cause the unit to go into sleep mode or to power-offcan be limited or prevented. The identity of the driver is determined bythe use of a unique driver ID, for example, a portable memory deviceissued to the operator and operable with a portable memory device reader241, such as a smart card or contact memory button. The ability tostart, move, or disable the vehicle can be controlled by or contingentupon an accurate identification of the driver.

Referring to FIG. 4, data acquisition and recording 130 encompassesacquiring data from the vehicle mileage sensing system, the vehicle ECM,GPS, driver input, and data portal 235. The on-board recorder 200 isconnected to the ECM of the vehicle through a data bus, such as an SAEJ1708, J1850 or J1939 data bus connected through the ECM interface 225.The data on the bus is translated into an RS232 signal via a commercialoff-the-shelf data translator and fed into the on-board recorderprocessor 205 and memory 210. The vehicle mileage sensing systeminterface 220 is formed, for example, by hard-wiring on-board recorder200 to the vehicle's magnetic speed sensor. Recorder 200 includes aGlobal Positioning System (GPS) receiver which forms satellite interface230 and derives its input signal from an antenna located on the interioror exterior of the vehicle.

Mileage can be determined from only the ECM or through a broadcasting ofan odometer reading from a vehicle dashboard, such as on a SAE J 1708MID 140 bus. Alternatively, data received from the vehicle mileagesensing system, such as a speed sensor positioned at the transmissiontail shaft of a vehicle can be automatically calibrated, for example, bycomparing the data to mileage determined from GPS or through GPS mappingfrom a central server. The device can be automatically re-calibrated, byprogramming recorder 200 with the size and wear of the vehicle's tiresand/or for different gear ratios. Recorder 200 can then provide thecalibrated mileage to at least one of the odometer display and the ECM.Vehicle mileage can also be calibrated by using the GPS mapping at thecentral server and then sending the calibration back to the vehicle.

Recorder 200 automatically, continuously records the vehicle operatingdata as raw vehicle operating data obtained from the vehicle mileagesensing system and the ECM, and records GPS data at a set period time,for example, every fifteen minutes. GPS data can also be recorded uponthe detection of a specific event, such as a change in duty status, oroperating parameter, such as the engine being off for more than aspecified period of time. To determine the hours of service, thedriver's duty status throughout the day is also determined. Duty statusincludes driving-on duty, not driving-on duty, off duty, and sleeperberth. Each change in duty status can be manually input to recorder 200by the driver using duty status buttons 244 and recorded with a time anddate stamp obtained via GPS. Certain changes in duty status can also bedetermined automatically by recorder 200, as discussed below.

Data processing 140 creates an HOS log 141 and an IFTA log 142 from theraw data, and compares the HOS log to applicable regulations todetermine whether the driver is in-compliance with HOS regulations. Amore detailed exceptions report can be created from the comparison ofthe HOS log to applicable regulations that provide the detail of thecomparison. In creating the HOS log, recorder 200 continuouslycalculates the-time the driver has been in each duty status over thecourse of a day. The HOS log includes the time per duty status for eightconsecutive days, including a calculation of the total hours driventoday, total hours on duty for the past seven days, and total hours onduty for the past eight days. The hours of service log is typicallycreated from date, time, mileage and duty status.

In creating the IFTA log, at every acquisition of data from GPS, forexample, every fifteen minutes, the miles driven over that time periodare calculated from mileage data obtained from the vehicle mileagesensing system and/or ECM, and recorded with a location, time, and datestamp obtained from the GPS data. A fuel tax report is then created,preferably by an external server, such as the host server or a secondserver communicating with the host server, having the requisite softwareto create a report in compliance with IFTA regulations, from the IFTAlog and any required fuel purchase information.

Data processing 140 can also include an automatic determination ofchange in duty status from off-duty to driving on-duty. By recording thetime when the vehicle starts to move, as determined by the ECMindicating engine use, i.e., that the vehicle has been started, and bythe vehicle mileage sensing system or ECM indicating motion, recorder200 automatically records a change of duty status to driving-on duty atthat time. By recording the time when the engine is turned off for apredetermined period, such as four minutes, recorder 200 automaticallyprompts the driver to input a change of duty status to not driving-onduty, off duty, or sleeper berth. Also, by recording the time when theengine remains on but the vehicle is not moving (determined from, forexample, either a speed of zero obtained from the ECM or there being nochange in mileage) for a predetermined period, such as four minutes,recorder 200 can automatically prompt the driver to input a change ofduty status to not driving-on duty, off duty, or sleeper berth. Off dutystatus is automatically determined at the time the driver logs out fromrecorder 200, for example, by removing the smart card from smart cardreader 241. Alternatively, the driver can use the keys to indicateoff-duty status while leaving the card in the reader.

Data reporting 150 includes using recorder 200 to provide information tothe driver, as discussed above, displaying on display device 250 thehours of service log and compliance status, with display 250 andindicator lights 246. An additional display tablet can be connected torecorder 200 to display the hours of service log in grid form. Forexample, operator's total hours driven today, total hours on duty today,total miles driven today, total hours on duty for seven days, totalhours on duty for eight days, and the operator's changes in duty statusand the times the changes occurred are displayed.

Data reporting 150 also encompasses the ability of system 100 toautomatically upload the hours of service log and the fuel tax log to areceiver external to the vehicle using a wireless telecommunicationsnetwork. Recorder 200 also emits, such as periodically or continuously,a signal representative of the compliance status to a second receiverexternal to the vehicle and under control of authorities, such as lawenforcement, carrier management, regulatory agencies or other approvedinspector or agent. In addition, the compliance status, HOS logs or amore detailed exceptions report can be uploaded to a second receiverexternal to the vehicle when recorder 200 is queried.

Recorder 200 is configured to automatically attempt to transmit data toa host server via the wireless telecommunications network's off-peakhours, e.g., at a pre-determined period of time (e.g., 1:00 am-5:00 am)that is selected because it is available at low cost. A wirelesstelecommunications network made up of pager networks, cell phonenetworks and wide area networks provides low cost options. Other optionsare an infrared connection, a radio connection, and a satelliteconnection. Recorder 200 is programmed to seek a single wirelesstelecommunications network to upload data to a host server.Alternatively, recorder 200 can be programmed to seek various wirelesstelecommunications networks to upload data to a host server, from theleast cost to the next most expensive cost and so on until the devicefinds such a data link and uploads its data. If after a predeterminedtime period for performing an upload, such as fourteen days, upload hasnot been successful, each day's HOS log, and IFTA log, and alternativelyan exceptions report as well, can be uploaded whenever the recordercomes into contact with the predetermined method of uploading data, orcan be uploaded over a satellite connection. Data is stored on recorder200 for not less than 14 consecutive days and is organized by driver forhours of service purposes and/or by vehicle for fuel tax reportingpurposes.

By continuously emitting a signal indicating the compliance status ofthe driver, recorder 200 provides a way whereby authorized federal,state or local officials can immediately check the status of a driver'shours of service. Authorities receive this signal whenever the vehicleis within a predetermined range of the second receiver located, forexample in a hand-held device, law enforcement vehicle, weigh station,or along a highway. The entire hours of service log can be displayed onrecorder 200 or on an electronic display or tablet connected thereto, ordownloaded, when recorder 200 is queried. Data can be downloaded to lawenforcement personnel using a receiver tied to a computer, for example;in the law enforcement vehicle, that wirelessly interrogates recorder200 and displays the data, by using a handheld device in the possessionof a law enforcement officer that wirelessly interrogates recorder 200and displays the data, or by using a wired connection through a portinside or outside of the vehicle.

The capability can also be provided to download information from a hostserver to the recorder. For example, using the communication link bywhich data is downloaded to the host server, the host server can alsocommunicate data to recorder 200 at the end of the daily upload cycle.Data transmitted can include driver regime, such as 7 day/60 hour or 8day/70 hour regime. The host server can also communicate with recorder200 as desired via a wireless telecommunications network to ascertaininformation, such as compliance status, location as of the last GPSrecording and remaining HOS.

Referring to FIG. 5, the overall process includes driver and vehicleidentification and verification 505, acquiring and recording GPS data atpre-determined intervals, for example, every 15 minutes 510, acquiringmileage and ECM data, for example, continuously, recording mileage andECM data, for example, at least every 15 minutes, 515, determining dutystatus from driver input and/or automatically and recording duty status520, calculating total hours per day in each duty status to create anHOS log 530, recording latitude and longitude for fuel tax reporting535, comparing the HOS log to regulations to determine compliance,uploading compliance status or a detailed exceptions report to federal,national, state, provincial or local authorities 550 continuously,periodically or upon receipt of authority's or driver request, uploadingto the host server 560, for example, daily, and uploading to therecorder display 570, for example, every five minutes.

Recorder 200 automatically records data formatted to meet home countrylegal requirements and country of operation legal requirements. Forexample, a driver whose home country is Mexico, may operate a vehicleover a period of time in the United States. The operation of the vehiclewithin these countries, and their respective states, provincial or localjurisdictions triggers different reporting requirements to comply withrespective HOS laws or regulations. Recorder 200 simultaneously recordshours of service and/or fuel tax information that is country-specific,such as for the United States, Canada, and Mexico, and has multi-lingualreporting capability, such as English, French and/or Spanish.

As seen in FIG. 6, a graphical representation of an hours of service logincludes duty status (off-duty, sleeper berth, driving, and on duty-notdriving) on the vertical axis, and hours of the day on the horizontalaxis. The log line indicates each change in duty status, the time thechange occurred, and the hours within each duty status between changes.In the example shown for Day 1, the driver was in “off duty” status for10 hours (midnight to 10 am on Day 1), followed by five hours of on“duty-driving” (10 am to 3 pm on Day 1), followed by a “sleeper berth”period of five hours (3 pm to 8 pm). The driver was then back on duty“driving” for another five hours (8 pm to 1 am on Day 2) when the driverwas pulled over for a routine roadside inspection or weigh station. Inthis situation, the driver was in compliance with the hours of serviceregulations. Accordingly, a signal representing a compliance status(in-compliance state) would have been emitted by the on-board recorderduring the inspection. The law enforcement officer would have knownbefore inspecting the hours of service log shown in FIG. 6 that thedriver was already in compliance.

A complete display of an hours of service log can provide eight suchgraphical representations, one for each of the eight days, and a summaryof the total hours driven today, total hours on duty for seven days andtotal hours on duty for eight days. As seen in FIG. 7. the hours ofservice log shown in FIG. 6 can be displayed separately from recorder200. For example, an external display device 700 is connected torecorder 200 to provide a more detailed review of recorded data.External display device 700, such as an electronic tablet connectedwirelessly or through a wired connection such as a USB connection withrecorder 200, has a relatively large display 750 for viewing detailedHOS logs (see FIG. 6) that are not as easily viewed on the display 250of recorder 200. The external display device 700 includes a devicefunctioning indicator 710, compliance status indicators 720, a home oroperating country selector 730, driver selectors or indicators 740, aduty status selector 760 and a data transmission port 770, such as a USBconnection or wireless transceiver for wirelessly communicating withrecorder 200.

Referring to FIG. 8, a device 800 for receiving a signal indicating acompliance status of a driver or vehicle has an “in-compliance”indicator 810, an “out-of-compliance” indicator 820, an input/keypad830, and a receiver 840 for receiving emitted compliance status signalsfrom nearby recorders 200. Device 800 can be powered from a lawenforcement officer's vehicle (such as plugged into a cigarettelighter), or battery, and can be a handheld device that is used tomonitor passing and nearby vehicles for HOS compliance status. Recorder200 can have a short range RF transmitter which broadcasts the driver'sHOS compliance status, electronic vehicle license plate, drivers riskfactor based on past records, etc. The receiver can be an RF receiverdistributed to state, local, and federal authorities providing snapshotmonitoring of the status of drivers (HOS compliant or non-compliant),high risk drivers and vehicles at toll gates and border crossings.

A number of embodiments of the invention have been described.Nevertheless, it will be understood that various modifications may bemade without departing from the spirit and scope of the invention. Forexample, the on-board recorder may be configured to include one or moreof the following features.

Recorder 200 can include a biometric reader for verifying the identityof the driver using, for example, facial, retinal or thumbprintrecognition. The identity data is compared to a database within recorder200 to verify the identity of the driver by matching the biometric witha specific driver. The unique driver ID can be a Transportation WorkerIdentification Card (TWIC) currently being developed by theTransportation Security Administration (TSA) or a commercial driver'slicense (CDL) issued by various state or federal governments. Thevehicle can be disabled if the identity of the driver cannot be verifiedafter some predetermined time.

Camera 249 can be a miniature camera, such as with IR lighting for nightdriving, positioned on the front face of recorder 200 for visualanalyzing the driver. The camera is used to identify the driver andvisually tie the driver to the HOS data. Facial recognition, retinal orIRIS mapping, and driver behavior can be periodically assessed such asfor drowsy driver syndrome from the recorder or an external source, suchas through an external host server. The digital camera feature can beused for gate authorization by sending the drivers' ID and photographahead to a destination, such as a shipping dock or border crossing. Thecamera feature can be used for on-board documentation to the centralserver. Once the vehicle is in the non-moving and park mode the digitalcamera can also be used as a FAX/Scanner.

The portable memory device carried by the driver, for example, the smartcard or contact memory button (such as the IBUTTON® device availablefrom Maxim Integrated Products, Inc. of Sunnyvale, Calif.), can beconfigured to retain driver identity data, driving regime (such as, 7day or 8 day regime), and the driver's hours of service log such thatthis information is automatically downloaded from the portable memorydevice to recorder 200 whenever a driver logs into a vehicle. In thisway, the driver's hours of service log and related information can betransferred from one vehicle to another as the driver changes vehicle.Such data can also be downloaded into recorder 200 from the fleetcarrier via several methods, for example, a wired connection at thefleet terminal, a wireless connection at the fleet terminal and/or awireless download at any location within the range of a wirelesstelecommunications network. The portable memory device can include aprogrammable logic controller, such as an electrically erasable,programmable, read-only memory (EEPROM) of flash EEPROM.

Additional information that can be stored on the portable memory deviceincludes the driver's current driving regime, the commercial driverlicense number (CDL #), commercial driver endorsements (e.g., HAZMAT),traffic violations and high risk driver data (e.g., DWI convictions).Transactions such as the last vehicle driven can also be stored on thedriver card. Portable memory device technology, such as the IBUTTON®,can be used to transfer fuel purchase information about the vehicleand/or driver to a fuel pump and/or from the fuel pump to recorder 200.Alternatively, or in combination, infrared and RFID technology can beused to transfer data to and from recorder 200 to a user ID card orother external data source.

Recorder 200 can separately record each driver's duty status when morethan one driver is driving the vehicle, for example team driving. Whilethe hours of service for a particular driver are transferred, forexample, by a wireless telecommunications network connection or portablememory device, when the driver moves to a new vehicle, the IFTA logs,which are vehicle dependent, remain with the recorder on the oldvehicle.

IFTA reports identify the miles driven in each jurisdiction. Bordercrossings, for example, between states, countries, and provinces, can bedetermined by the driver inputting to recorder 200 when a border iscrossed, by mapping software on an external server, or by mappingsoftware on recorder 200. Recorder 200 can emit a signal indicatingwhether the recorder is present and thus recording data for compliancewith applicable IFTA laws or regulations, and can emit safety relatedinformation such as tire pressure.

For each change of duty status, whether input manually or determinedautomatically, location as determined by GPS can be recorded. If avehicle is equipped with an Intelligent Dash Board with speedometer, ondash odometer and fuel gage 225, data can be collected by recorder 200from the Intelligent Dash Board rather than through the vehicle mileagesensing system interface 220.

The data processing 140 and data reporting 150 sections can also providethe capability of data encryption to ensure data integrity and toprevent tampering by the vehicle operator. However, the driver and/orcarrier can be permitted to modify the operating data, and the processorincludes a track changes function that records any alterations ofoperating data. Recording 200 can also provide the capability ofauthenticating the recipient of data such that data is only available toauthorized users.

Recorder 200 can prompt the driver to review and verify that all entriesare accurate prior to uploading data to the carrier. Recorder 200 canfurther prompt the driver to certify that all entries made by the driverare true and correct or that recorder 200 is operating properly. Ifrecorder 200 malfunctions, the recorder can notify the driver visually,audibly and/or using a text message, prompt the driver to revert to apaper log, and/or emit an out-of-compliance signal. If recorder 200determines that the vehicle is moving but no driver is logged on, avisual/audio/or text warning is provided to the driver signaling thatthe driver is not logged-in, and an out-of-compliance signal is emitted.Recorder 200 can also warn the driver when the driver is approaching themaximum limitations established by the hours of service laws orregulations. Recorder 200 can also upload such a warning to the carrier.

To limit “double counting,” whereby a driver uses a paper log book whenrecorder 200 is on-board, recorder 200 can emit a signal indicating thatrecorder 200 is on-board the vehicle. Recorder 200 has logic built in toaccount for, for example, gaps in miles or time to ensure the driverdoes not tamper with recorder 200, such as by disconnecting the powersource, pulling a fuse, or similar tampering.

Recorder 200 continually or periodically performs self-testing and canprompt the driver to troubleshoot for system errors and systemrebooting. Recorder 200 can self-test upon demand from law enforcement.

WIFI or BLUETOOTH technology can be utilized to facilitate data transferand/or permit the communication of many different devices to form acommunication network. BLUETOOTH technology can be used to permit thedownloading of fuel purchase information to recorder 200 and/or as thecommunication protocol for the recorder itself in communications withlaw enforcement or any other data transfer.

Recorder 200 can have a short range RF transmitter which broadcasts thedriver's HOS compliance status, electronic vehicle license plate,driver's risk factor based on past records, etc. The receiver can be anRF receiver distributed to state, local, and federal authorities for asnapshot monitoring status of drivers (HOS compliant or non compliant)high risk drivers and vehicles at toll gates and border crossings, andfor Homeland Security purposes generally. The receiver can plug into thecigarette lighter of the law enforcement vehicle, similar power sourceor be positioned within a handheld device. A non-compliant driver can beidentified by recorder 200 emitting short range signals, such as 315 MHZor 434 MHZ (approximately 200 ft) RF signals, which can be detected byauthorities. The receiver held by authorities can be a 315 MHZ or 434MHZ RF device. The data exchange is dependent upon an authenticationprocess, whereby only authorized users (the authorities) can access thedata. The authorities can then be alerted while driving past a vehicleon the highway or when sitting along an interstate and monitoring forviolators. Once a violation has been detected the authorities can obtaina detailed log from the recorder via a hard connection or a wirelessconnection, such as BLUETOOTH or WIFI adapter in the USB data port ofrecorder 200. Also the non compliant driver status can be broadcasted onthe SAE J1708/1587 data bus and the RS-232 port from the recorder. Asanother method the RS-232 and/or SAE J1708 data can allow existingtelecommunication products on the vehicle such as QUALCOMM®, XATA® andPEOPLENET® to transmit the driver log report status. Also, as anothermethod the RS232, SAE J1708 or USB data port can allow the driver logsto be downloaded via WIFI or BLUETOOTH adapters or devices at WIFI hotspots at truck stops, for example, SIRICOMM has incorporated WIFI hotspots at Pilot Service Centers, and WIFI Hot(s) Networks are planned atweigh stations, toll gates, and Fleet Terminals.

Vehicles emitting an in-compliance signal can pass through a checkpointor roadside inspection without further delay and those that are notin-compliance can be stopped for further investigation. Recorder 200 canbe queried to generate a driver's hours of service graph and display thegraph, for example, on a display tablet that can be connected torecorder 200. Electronic tablet 700 can be equipped with a rechargeablebattery, such as a NiCd battery or a standard NiCad battery pack used onvideo cameras. The electronic tablet device 700 can include an antennafor all types of wireless communication and a connection permittingwired communication. The electronic tablet 700 can include a USB port sothat printers and other devices can communicate to the electronic table700. The recorder can be provided with a USB Port to form a direct,non-wireless connection to the tablet.

Recorder 200 can also be provided with the option of detecting whetheror not a trailer is tethered to the vehicle. If tethered, recorder 200connects to a PLC chip located in the trailer from the ABS TrailerModule that contains the trailer's ID number and related data and a PLCreceiver chip located in the recorder. The trailer ID information can beobtained from various sources, for example, via a PLC4Trucks power linecommunications, such as defined in SAE J2497. If the fleet operatorwants to locate that particular trailer it can access the PLC networkchip via cell or pager network, or via satellite, through recorder 200.

The Recorder 200 can be equipped with a Tractor PLC ID transmitter chipand the driver log information can be downloaded from a Trailer TrackingSystem, such as TERION®, using a SAE J 2497 power line communicationprotocol. This method allows the driver's log report along with atractor ID to be sent through an existing power line, for example, usinga standard SAE J560 tractor/trailer connector and SAE J2497 protocol toa trailer communication wireless product.

II. Automated At-the-Pump Management of Vehicle Fuel Purchases

FIGS. 9, 10 and 11 illustrate embodiments of a system, method, andapparatus for automated at-the-pump management of vehicle fuel purchasesat a fuel station “S”. As shown in FIG. 9, the exemplary vehicle 900(e.g., heavy-duty tractor/trailer combination) includes an electronicon-board recorder 901 (EOBR), such as recorder 200 described above, anda data communications adapter 902 operatively connected to an existingvehicle data bus 903 including, for example, SAE J1708/1587, SAE J1708,SAE J1850, SAE J1939, SAE J2497, SAE J560, OB-2, CAN, and RS-232. Thedata communications adapter 902 receives and converts the serial packedvehicle data for transmission via wired or wireless communication means.The exemplary data communications adapter 902 incorporates an embeddedNFC/RFID transceiver 905, a microcontroller 906, and hardware 907comprising BLUETOOTH and WIFI communications modules. In alternativeembodiments, the data communications adapter 902 is integrated with theEOBR 901, which may also comprise NFC technology and BLUETOOTH, WIFI,and cellular communications modules.

The present disclosure is implemented utilizing a Mobile Device 910(e.g., smartphone) assigned to and carried by the vehicle driver, andincorporating one or more of the elements and features described above.The exemplary Mobile Device 910 comprises NFC technology allowing it towirelessly read/write and otherwise communicate data to and from otherNFC enabled devices, such as the EOBR 901 and data communicationsadapter 902. In an exemplary embodiment, the disclosure requires anassociation between the driver, the vehicle 900, and the driver's MobileDevice 910. As referenced in FIG. 9, the driver carries an NFC/RFIDidentification card 915 which electronically stores driver dataincluding, for example, first and last name, e-mail address, andtelephone number. This same driver data may also be pre-stored in thepersistent (non-volatile) memory of the Mobile Device 910—e.g., storedat the time the Mobile Device 910 is assigned to the driver.

Referring to FIGS. 9 and 10 and the flow diagram of FIG. 11, theexemplary method for automated at-the-pump management of vehicle fuelpurchases begins as the vehicle 900 enters the fuel station, asindicated at 921 in FIG. 11. At the fuel station, using the NFC-enabledMobile Device 910 the driver electronically reads the data stored on hisNFC/RFID driver identification card 915, as indicated at 922 in FIG. 11.The driver data is wirelessly communicated from the identification card915 to the Mobile Device 910, and compared in realtime using theprocessing logic of the Mobile Device 910 to the driver data pre-storedin the persistent memory (or cloud storage). If the driver data readfrom the identification card 915 matches the data stored in the MobileDevice 910 or cloud storage, the driver will be prompted to enter averification key (e.g., 4-character code or password) using an inputkeypad of the Mobile Device 910. In an alternative embodiment, theverification key may comprise a voice code spoken by the driver into themicrophone of the Mobile Device 910, and compared using voicerecognition software to an audio (voice) clip pre-stored in memory. Inanother embodiment, the verification key may comprise a driver thumbprint captured using the touchscreen of the Mobile Device 910, andcompared to a thumb print pre-stored in memory. In yet anotherembodiment, the verification key may comprise a digital photograph ofthe driver's face captured using the camera of the Mobile Device 910,and compared using facial recognition software to a digital photographpre-stored in memory. In further alternative embodiments, theverification key may utilize other biometric data, such as a retinalidentifier. The verification key may also comprises a hand drawn patternentered by the driver on the display screen of the Mobile Device 910,such as disclosed in published U.S. Patent Application, Publication No.US/2013/0212674-A1. The complete disclosure of this prior publication isincorporated herein by reference.

After successful driver verification, as indicated at 923 in FIG. 11,the date and time the driver's identification card 915 was read and theexact GPS location where the reading occurred, collectively “eventsetting”, is recorded in the memory of the Mobile Device 910, asindicated at 924 in FIG. 11, and may be communicated (via WIFI, cellularor satellite transmission) to the EOBR 901 for storage and/or a remoteterminal “R” located at a corporate office. The driver then uses theMobile Device 910, as indicated at 925 in FIG. 11, to capture vehicledata communicated via NFC/RFID transmission (e.g., using “bump datatransfer”) from the data communications adapter 902 connected to thevehicle data bus 903. The vehicle data may comprise, for example,current fuel level, mileage, trailer identification, engine VIN, engineoil level, oil analysis, and diagnostic fault codes. As shown in FIG.10, after capturing the vehicle data, the driver carries the MobileDevice 910 to a fuel control terminal “P” located at the fuel pump ofstation “S”.

The exemplary fuel control terminal “P” may comprise integrated and/orexternally connected hardware (such as transponders, transverters,repreaters, transceivers, transmitters, receivers, antennas, and thelike), software, firmware, wireless technology including WIFI andBLUETOOTH, and NFC and other RFID standards enabling wirelesstransmission and receipt of signals and data (NFC tag reading/rewriting)at 125 kHz, 13 MHz, 315 MHz, 433-434 MHz, and other frequencies. In oneembodiment, the fuel control terminal may comprise a microcontroller, 2GB RAM memory, 8 GB solid state hard drive, keypad, display screen, andcommunications technology comprising hard wire Cat5/6—TCP/IP, NFC/RFIDdevices, BLUETOOTH device, cellular 3G/4G, and WIFI802.11B/G—(WPA2-PSK). The fuel control terminal may also incorporate acellular modem to communicate collected data directly to the remoteterminal, EOBR, vehicle telematics (information and communicationstechnology, or ITC), sealed splice pack system (e.g., VES-PAC™ inlinecircuit fuse holder), and/or other vehicle-mounted or integratedcomputing/communications unit.

In the exemplary method, the fuel control terminal “P” receives thedriver data and vehicle data (e.g., via NFC bump transfer) from theMobile Device 910, as indicated at 926 in FIG. 11, and then wirelesslytransmits this data to the remote terminal “R” located at the corporateoffice, as indicated at 927 in FIG. 11. The data is authenticated at theremote terminal “R” using software designed to confirm the driver'sassociation with the vehicle 900 and Mobile Device 910, and to processcurrent fuel level and miles driven since last fueling. After the datais authenticated, as indicated at 928 in FIG. 11, an authorizationsignal is transmitted from the remote terminal “R” to the at-the-pumpfuel control terminal “P”, as indicated at 929 in FIG. 11. Theauthorization signal allows the driver to dispense a pre-determinedquantity of fuel from a station pump to the vehicle 900 (including thetrailer “reefer”), as indicated at 930 in FIG. 11. After fueling,purchase data including fuel cost and gallons dispensed may bewirelessly transmitted (e.g., via NFC bump transfer), as indicated at931 in FIG. 11, from the fuel control terminal to the Mobile Device, orfrom the fuel control terminal directly to the remote terminal, EOBR, orvehicle telematics via cellular or satellite communication.

In the exemplary embodiments described above, certain data istransmitted via short-range communication technologies, such as NFC.This short-range transmission reduces the likelihood of unwantedinterception, and is particularly suited for crowded areas wherecorrelating a signal with its transmitting physical device (and byextension, its user) becomes difficult. Additionally, the connectionbetween two NFC-enabled devices is automatically established quickly,generally in less than a tenth of a second, and conveniently.

The exemplary Mobile Device 910 incorporates “active” NFC technologyenabling the device to read and write to other active or passive NFCdevices (e.g., tags) incorporated in the fuel control terminal “P”, EOBR901, and data communications adapter 902. In an alternative embodiment,the Mobile Device 910 may activate passive NFC tags in the fuel controlterminal “P”, EOBR 901, and/or data communications adapter 902 to placethe associated device in a “discoverable” mode. Once activated ordiscovered, the Mobile Device 910 may wirelessly connect to the deviceand communicate data using BLUETOOTH or other short range communicationstechnology.

III. Automated Vehicle Diagnostics

In further exemplary embodiments, the present disclosure comprisessystems, methods, and apparatus for diagnosing and managing vehiclefaults. As previously described, the vehicle (e.g., heavy-dutytractor/trailer combination) includes an electronic on-board recorder(EOBR) and a data communications adapter operatively connected to anexisting vehicle data bus including, for example, SAE J1708/1587, SAEJ1708, SAE J1850, SAE J1939, SAE J2497, SAE J560, OB-2, CAN, and RS-232.The exemplary data communications adapter incorporates an embeddedNFC/RFID transceiver, a microcontroller, and hardware comprisingBLUETOOTH and WIFI communications modules. The data communicationsadapter may be integrated with the EOBR, which may also comprise NFCtechnology and BLUETOOTH, WIFI, and cellular communications modules.

In the present application, the exemplary data communications adapterreceives, converts, stores, and transmits serial packed vehiclediagnostic data. The diagnostic data can be wirelessly captured from thedata communications adapter using Mobile Device, describe above, or adedicated NFC-enabled portable memory device, such as the IBUTTON®device. The IBUTTON® device automatically wirelessly receives vehiclediagnostic data by simply touching the data communications adapter.After receiving the diagnostic data transmitted by the adapter, theIBUTTON® device can be conveniently carried by the driver or other userto any remote terminal location (e.g., corporate office, vehicle partsstore, vehicle service facility), and the diagnostic data transferred tothe remote terminal to process the vehicle fault codes. The vehiclefaults may also be transmitted from the IBUTTON® device directly to thevehicle's EOBR via NFC bump data transfer or other communication means.

In further embodiments of the present disclosure, the driver's MobileDevice and/or the EOBR may comprise or interface with hardware,software, and firmware designed to monitor driver health conditionsincluding (e.g.) oxygen level, heart rate, breathing patterns, bloodpressure, pulse, brainwave patterns, pupil dilation, glucose level, andblood alcohol level. The hardware/sensors may be integrated with thevehicle steering wheel or with other components of the vehicle. Thedriver health data may be transmitted in realtime from the Mobile Deviceor EOBR directly to the remote terminal (located at the corporateoffice).

In other applications, the driver's Mobile Device and/or EOBR mayutilize GPS road data to calculate and store any history of vehicle overspeeding, and may then report that data to the remote terminal or cloudstorage. Mobile Device and/or EOBR may also notify the driver ofupcoming high accident areas and work zones, and may record the driver'sreaction and maneuvering through such areas.

For the purposes of describing and defining the present invention it isnoted that the use of relative terms, such as “substantially”,“generally”, “approximately”, and the like, are utilized herein torepresent an inherent degree of uncertainty that may be attributed toany quantitative comparison, value, measurement, or otherrepresentation. These terms are also utilized herein to represent thedegree by which a quantitative representation may vary from a statedreference without resulting in a change in the basic function of thesubject matter at issue.

Exemplary embodiments of the present invention are described above. Noelement, act, or instruction used in this description should beconstrued as important, necessary, critical, or essential to theinvention unless explicitly described as such. Although only a few ofthe exemplary embodiments have been described in detail herein, thoseskilled in the art will readily appreciate that many modifications arepossible in these exemplary embodiments without materially departingfrom the novel teachings and advantages of this invention. Accordingly,all such modifications are intended to be included within the scope ofthis invention as defined in the appended claims.

In the claims, any means-plus-function clauses are intended to cover thestructures described herein as performing the recited function and notonly structural equivalents, but also equivalent structures. Thus,although a nail and a screw may not be structural equivalents in that anail employs a cylindrical surface to secure wooden parts together,whereas a screw employs a helical surface, in the environment offastening wooden parts, a nail and a screw may be equivalent structures.Unless the exact language “means for” (performing a particular functionor step) is recited in the claims, a construction under 35 U.S.C. §112(f) [or 6th paragraph/pre-AIA] is not intended. Specifically, use ofthe claim term “input means” is not intended to invoke a constructionunder § 112(f). Additionally, it is not intended that the scope ofpatent protection afforded the present invention be defined by readinginto any claim a limitation found herein that does not explicitly appearin the claim itself.

I claim:
 1. An onboard electronic system for logging and reportingdriver activity and operation data of a vehicle, said system comprising:an onboard recorder operatively connected to a data bus of the vehicleand configured to continuously electronically monitor and obtain vehicleoperation data comprising vehicle fuel consumption data and vehiclemileage data, and said onboard recorder comprising a processor, atransmitter, and a memory device for recording and storing said vehicleoperation data; said transmitter adapted for transmitting said vehicleoperation data from said onboard recorder to a remote terminal outsideof the vehicle; data processing software operable for: (i) generating afuel data report using said vehicle operation data continuouslymonitored, obtained and calculated from the data bus of the vehicle andtransmitted from the onboard recorder to the remote terminal; and (ii)determining based on the fuel data report whether a driver satisfies avehicle operation requirement established by an authority, the authoritybeing selected from a group consisting of carrier management, regulatoryagency, approved inspector and agent.
 2. The onboard electronic systemaccording to claim 1, wherein the fuel data report comprises GPSlocation data obtained from a global navigation satellite system.
 3. Theonboard electronic system according to claim 2, wherein the fuel datareport comprises time data obtained from at least one of the vehicledata bus and the global navigation satellite system.
 4. The onboardelectronic system according to claim 2, wherein the fuel data reportcomprises date data obtained from at least one of the vehicle data busand a global navigation satellite system.
 5. The onboard electronicsystem according to claim 1, wherein the fuel data report comprisesmiles traveled by the vehicle at time intervals.
 6. The onboardelectronic system according to claim 5, wherein the fuel data reportcomprises location, time, and date recorded at each time interval. 7.The onboard electronic system according to claim 1, wherein the fueldata report for a current day is automatically uploaded to the remoteterminal.
 8. The onboard electronic system according to claim 7, whereinthe fuel data report for a previous day is automatically uploaded to theremote terminal.
 9. The onboard electronic system according to claim 8,wherein the fuel data report for a day prior to the previous day isautomatically uploaded to the remote terminal.
 10. The onboardelectronic system according to claim 1, wherein the fuel data reportcomprises a fuel tax report.
 11. The onboard electronic system accordingto claim 1, and comprising a biometric reading device for identifyingthe driver of the vehicle using biometric data.
 12. The onboardelectronic system according to claim 1, wherein said onboard recorderfurther comprises an engine control module interface configured toconnect to the data bus of the vehicle.
 13. The onboard electronicsystem according to claim 1, wherein said onboard recorder furthercomprises at least one data portal configured to upload vehicleoperation data from the memory device to the remote terminal using awireless telecommunications network.
 14. The onboard electronic systemaccording to claim 1, and comprising a driver interface configured toelectronically record driver identification information input by thedriver.
 15. The onboard electronic system according to claim 1, andcomprising a driver interface configured to electronically record a dutystatus input by the vehicle driver.
 16. The onboard electronic systemaccording to claim 1, and comprising a wired connection between saidonboard recorder and the vehicle data bus.
 17. The onboard electronicsystem according to claim 1, and comprising a portable memory devicereader adapted for reading a portable memory device carried by thedriver and configured to electronically store driver identity data. 18.The onboard electronic system according to claim 1, and comprising acamera adapted for visually analyzing and identifying the driver of thevehicle.
 19. The onboard electronic system according to claim 1, andcomprising a self-test button configured to enable the driver toinitiate operability testing of said onboard recorder.
 20. The onboardelectronic system according to claim 1, wherein said onboard recorder isconfigured to operatively connect to a computer chip containing traileridentification information.